…ty check

Change-Id: Id7df987f0e9db4e5e2328534764ded397b6ac48d

…ty check

Change-Id: I34d5a8313304e3ac8bd53282de66ab1d3d1653a8

On msm-4.14 devices, when the proximity sensor is in use,
the smp2p-sleepstate IRQ is fired multiple times a second,
with each one holding a 200ms wakelock.
This is probably a bug in the DSP firmware.
To fix this, avoid using the proximity sensor in doze mode,
because sleep is preferred to turning off the screen.

Change-Id: I57750afd77267abdc49780f70636626d20e666ad

Author: Roman Birg <[email protected]>
Date:   Thu Feb 4 16:28:00 2016 -0800

    framework: move device key handler logic, fix gesture camera launch

    In order to make device camera gestures behave the same way as launching
    the camera by double tapping the power button, route DeviceKeyHandler
    logic through the GestureLauncherService.

    A callback is used in order to avoid publishing the
    GestureLauncherService into the System service registry, because the
    KeyHandler code cannot directly access services local to the system
    process.

    OPO-427

    Change-Id: I2a8860b278f65ccf31bfee151513d8a23ab746c5
    Signed-off-by: Roman Birg <[email protected]>

Author: Roman Birg <[email protected]>
Date:   Sat Feb 13 09:08:21 2016 -0800

    KeyHandler: don't break old interfaces

    Causing bootloops on devices, don't break old interfaces in the
    framework.

    OPO-427

    Change-Id: I49473b057bc4ed4710e9092c76e41c6a8134d2de
    Signed-off-by: Roman Birg <[email protected]>

Author: Roman Birg <[email protected]>
Date:   Tue Feb 16 17:22:01 2016 -0800

    SystemUI: handle camera launch gesture from keyhadler

    Includes partial reverts:

        Revert "KeyHandler: don't break old interfaces"
        This reverts commit 31ecbdc5fcc1263e9028107858565d951798fd93.

        Revert "framework: move device key handler logic, fix gesture camera launch"
        This reverts commit db1b4e6e4880be1828342be9bc468d36565a2ef0.

    Ref: OPO-427

    Change-Id: Ic15543a8f63ad4521ab0ab536d00224b0bd70f8c
    Signed-off-by: Roman Birg <[email protected]>

Author: Michael Bestas <[email protected]>
Date:   Sat Feb 20 00:56:47 2016 +0200

    SystemUI: Don't vibrate on touchscreen camera gesture

    * This is usually handled in device-specific keyhandler,
      where vibration is optional and has the same duration
      in all gestures

    Change-Id: I879671c9d6f785137d63b8b70de35f5d5020748d

Change-Id: Iba9211b7d342f618c4082c34d11663d89861607a
(cherry picked from commit b48ec290d5c734950b2ccfd56247fac72ea76331)

Change-Id: Ibc17db2878c026120e831bb587a2d00d55ba4856

Change-Id: Idc6da92fb41a780d01c961d676f61ae4b91d2a7b
CRs-Fixed: 3218447

Change-Id: Ie143a0489163177d3be3e0de280bc3ed0d017437
CRs-Fixed: 3218447

Now it's showing correct font for QS header clock, date and carrier text
after changing system font.

Change-Id: I75d7a065e93e17ebba01aa9cbe705ac6ab5a781d

A service that makes use of qcom's power off alarm feature
Eliminates the need of app specific implementation for said feature
Should work with any alarm app that uses AlarmManager.setAlarmClock

Change-Id: I2eb9610eee5dea520683512f0e5b8e374f33152a

Avoid system_server crash
Caused by: java.lang.NullPointerException: Attempt to invoke interface method 'long android.content.SharedPreferences.getLong(java.lang.String, long)' on a null object reference
	at com.android.server.power.PowerOffAlarmService.cancelPowerOffAlarm(PowerOffAlarmService.java:134)
	at com.android.server.power.PowerOffAlarmService.updateAlarms(PowerOffAlarmService.java:127)
	at com.android.server.power.PowerOffAlarmService.-$$Nest$mupdateAlarms(Unknown Source:0)
	at com.android.server.power.PowerOffAlarmService$1.onReceive(PowerOffAlarmService.java:117)
	at android.app.LoadedApk$ReceiverDispatcher$Args.lambda$getRunnable$0$android-app-LoadedApk$ReceiverDispatcher$Args(LoadedApk.java:1790)
	... 10 more

Fixes: d5400bde5ee3 ("base: Introduce PowerOffAlarmService")
Change-Id: Ib8dba98af6f27b2edd3ec85809e9f2f84894023a

 * maximum_capacity * design_capacity

Change-Id: Idfa9207cc8bd35469876f3094f3bc948741c94bf
Signed-off-by: Jyotiraditya Panda <[email protected]>
Signed-off-by: Adithya R <[email protected]>

Change-Id: Ic85d351558dea5a5446c5ebe468b0db9e8c99285

Change-Id: I69b9eb04afc16a3a5acbea8cd26b9f1c42a03d4c

* Match Settings behaviour
* Miracast does not need Wi-Fi connection, it's Wi-Fi Direct

Change-Id: I46c1394f35f993875beaaad547c9709a4355a342

Change-Id: I66751353944b4cf8a5b5827c3ce53129ec84f1e7

Change-Id: I15d0f9fee13647062c651219b527e01a539b6909

Change-Id: Ied86dcfb6179d936786273867a50610900f1c5e5

The QS panel explains how to add/remove tiles, however after
'SystemUI: Allow user to add/remove QS with one click' the
description is wrong. Update the string to suggest both ways.

Change-Id: I2912e9254f9ed14436119addc913fe9907dc7f4e

Change-Id: I8f7f88d6451371458632b7949ef74bedbeccbaf8

The Fingerprint HAL is not always reporting fingerprint removal success,
so report success on fingerprint removal if no error has occurred.

Change-Id: I28fe2767ecffc9a830a91f2a1f262fbeaac73a1a

From SQ3A.220605.009.A1

[ghostrider-reborn]
- Adapt to aosp, fix crash on click, misc cleanup

This squashes the following commits:
Author: Jake Weinstein <[email protected]>
Date:   Sat Jun 17 05:29:07 2023 +0900

    SystemUI: Apply "Remove smartspace flag" to KeyguardSmartspaceController

    Change-Id: I7bbd0767d69d54854db691f6c90188a33373f529

Author: Adithya R <[email protected]>
Date:   Thu May 18 10:40:11 2023 +0530

    fixup! SystemUI: Open google weather on tapping smartspace

    Add null check for smartspaceTarget before hijacking the intent.

    Fixes AOSPA/Tracker#5

    Change-Id: I1cf9057589f88ba1571a5068fb639cbe011f7a67

Author: Adithya R <[email protected]>
Date:   Thu Jan 26 12:32:39 2023 +0530

    SystemUI: Open google weather on tapping smartspace

    Since smartspace weather activity won't open due to
    caller package (Launcher3) not being google signed,
    hijack the intent to open the google app's exported
    weather activity, which behaves in the same fashion.

    Change-Id: Ic01ede73ab6253bcb301ac794985c3720c5beda3

Author: Ido Ben-Hur <[email protected]>
Date:   Wed Mar 15 11:21:00 2023 +0200

    SystemUI: smartspace: Adapt to 13-QPR2

    Change-Id: I142ee24fb02d2234fc1aec50b8d7ff03eba3d5cf
    Signed-off-by: aswin7469 <[email protected]>

Author: Adithya R <[email protected]>
Date:   Wed Jan 25 18:24:21 2023 +0530

    [WIP] SystemUI: Update smartspace to 13-QPR1

    Credits to https://github.com/BenzoRom/frameworks_packages_SystemUIGoogle (Jason Edson <[email protected]>) for SystemUIGoogle jar and resources.

    Change-Id: I82c310ca72a5b4ae33b414fda223d127abd0d8d2

Author: Adithya R <[email protected]>
Date:   Sat Oct 15 15:04:25 2022 +0000

    SystemUI: BcSmartspaceView: Allow setting current page

    Required by launcher smartspace.

    Change-Id: I51d7728b6b2d3d7dfb06e39d1c9363f89795b54f

Author: jhenrique09 <[email protected]>
Date:   Wed Oct 5 12:26:30 2022 +0900

    SystemUI: Smartspace: Fix music indication on doze/aod

    Change-Id: If375051a6bf44c67344ad05a4366b6cc663f15d9
    Signed-off-by: Omkar Chandorkar <[email protected]>

Author: Adithya R <[email protected]>
Date:   Thu Aug 18 19:11:14 2022 +0530

    SystemUI: Forward-port smartspace to Android 13

    Change-Id: Iddf5c22562b1858e3159fd939c54890e23b29063

Author: SahilSonar <[email protected]>
Date:   Mon Oct 16 16:01:54 2023 +0200

    SystemUI: Forward-port smartspace to Android 14

    Change-Id: Ie408c347613af96cf271735071c93e374ae9e06e

SystemUI: Remove top padding from smartspace date card

Matches other cards and prevents the content from being too close to
the page indicator.

Change-Id: I092055e36883095118ef281232fa3721b7c54aa7

SystemUI: Add missing permission for Smartspace.

11-19 10:05:22.800  3994  3994 W BcSmartspaceView: Unable to register Doze Always on content observer.
11-19 10:05:22.800  3994  3994 W BcSmartspaceView: java.lang.SecurityException: No access to content://settings/secure/doze_always_on: Neither user 10209 nor current process has android.permission.INTERACT_ACROSS_USERS_FULL.

Change-Id: I39444dd95621ccfbe1dfd737e357145014e440d0
Co-Authored-By: Anay Wadhera <[email protected]>
Co-Authored-By: Adithya R <[email protected]>

Change-Id: I33cd285efc022770b55dab01911ef9e166ba94b5

* Building error text
error: BcSmartspaceView is not abstract and does not override abstract method setBgHandler(Handler) in SmartspaceView
public class BcSmartspaceView extends FrameLayout implements BcSmartspaceDataPlugin.SmartspaceTargetListener, BcSmartspaceDataPlugin.SmartspaceView {

Signed-off-by: clarencelol <[email protected]>

Change-Id: I55df836bf545554eda95085bc71c7cbfca4cfcc5
Signed-off-by: Andrzej Perczak <[email protected]>
Signed-off-by: Pranav Vashi <[email protected]>
Signed-off-by: Omkar Chandorkar <[email protected]>

Author: Jesse Chan <[email protected]>
Date:   Tue May 26 21:17:59 2020 +0800

    SystemUI: support black theme for dark mode [1/3]

    Change-Id: I57cd53de8f2c1e4d445441b514875b6af915b858
    Signed-off-by: Jesse Chan <[email protected]>

Author: Michael Bestas <[email protected]>
Date:   Wed Aug 24 21:19:57 2022 +0300

    Don't skip theme application if it's already current

    This fixes black theme and font/icon shape customizations.

    Change-Id: I8c3d3b4634e1ac60d28e4d5ef20bf9c2015e2e18

Change-Id: I7ebc7064a538c5a5c6adfd05afede7a44e4856b0

Change-Id: Ia051f9966adedcfe21e44be965cbccaaeb20c073
Signed-off-by: Anushek Prasal <[email protected]>
Signed-off-by: Pranav Vashi <[email protected]>

Other (system) apps can use this to perform specific tasks,
such as for DOZE state.

Change-Id: I2c62767a60db58e3999de65fbf506e5cc137e28e

Automatically pause media when muted. Resume if unmuted within a minute.

Co-Authored-By: Stylogey <[email protected]>
Change-Id: I5d37478b3739309dcaae4eb6a0e4aac6c87f120f

* Settings->System->Gestures->Prevent ringing

core: Remove @Systemapi annotation for VOLUME_HUSH_CYCLE.

  This addition should not be annotated with @Systemapi because it
  creates an addition that fails the API test in user builds

Signed-off-by: rituj <[email protected]>
Co-authored-by: Evan Anderson <[email protected]>
Change-Id: I334bd165e970665ac5300d387a0ea6745748d3ad

The feature is ported from Oppo ColorOS.
With the options on, users can swipe down
on the screen to have a screenshot.
Original smali port by: wuxianlin

Change-Id: I87ed333f81e1259758ea899bf019061d8ab85fd0

base: Improvements for swipe to screenshot

* Cancel touch events when tap with three fingers

* Dyrex2004: Fix typos (Screnshot -> Screenshot)

Change-Id: I6e1228e4101aa357d1e26ca6d0db1c44428ef367

base: SwipeToScreenshot: Import MIUI implementation

Reverse engineered from Xiaomi/beryllium/beryllium:9/PKQ1.180729.001/9.2.25:user/release-keys

Change-Id: I1d5938457b7cc4c5ef1fec235d27d8a40526961a
Co-Authored-By: Tobias Merkel <[email protected]>
Signed-off-by: Omkar Chandorkar <[email protected]>

Apps like Messaging may be allowlisted to be unaffected by doze mode
using the allow-in-power-save permission, but prior to this change,
their jobs are still restricted from running when the device is idle,
leading to delayed processing. On the other hand, jobs scheduled by
packages that are user-exempted via the "Unrestricted" app battery
usage option do not experience such delays. This change causes system-
exempted packages to be treated the same as user-exempted packages.

Issue: calyxos#1525
Bug: 223643513
Test: CtsJobSchedulerTestCases
Change-Id: I6d95b3940e536e93aae4b2b48706069e964bdb99

…witch

Change-Id: Ia40124870ee548a561caa790c34caa50e9d3b809

Fixes: 8a7af5a9742863312b3dcef65cfdbd77f2660daf
Fixes: https://gitlab.com/LineageOS/issues/android/-/issues/8317
Change-Id: I2c059da77c54c4fea11bdbabd1dde752f74ca6cf

Change-Id: I1d8a28eee49056e73917c052180fd7328eb7fbd5

Technically, this should be fixed device side, but random failure when
HAL side fails shouldn't crash the system either.

Fixes: https://gitlab.com/LineageOS/issues/android/-/issues/8391
Change-Id: Iedd869cbd74e4a5535655c977b8ead74e8d5868d

And also Get rid of old and unused detail adapter
Some other minor improvements

Change-Id: Ifbbc6801c9fe28c65c86801d29fb76adf8ddcd95
Signed-off-by: Omkar Chandorkar <[email protected]>

Change-Id: I6157d91ca93a771b32bd2c3b859c19ed42efa469
Signed-off-by: Pranav <[email protected]>

Change-Id: Id0fcc1805f4144463b4d3f040fb4d2ea1644c1a2
Signed-off-by: Pranav <[email protected]>

Change-Id: I6c2cd0261885b656910feffe76d67e169d8523c8
Signed-off-by: Pranav <[email protected]>

* algorithms shouldn't be a static field since pins is an instance variable
* use stream API's to map and collect pin algorithms to an ArraySet

Fixes: 1d384463675effe0544a38ec137fa5021d571fc2 ("Cache pin algorithms in PinSet")
Signed-off-by: Adithya R <[email protected]>
Change-Id: I8a0cd85a350901b9900044cb536bd32b7cb40e02

Store normal callback references in PrivacyConfig, rather than
WeakReference. This prevents the callbacks from becoming phantom
reachable (finalized) shortly after SystemUI starts.

Prior to this change, devices with an overlay config to enable location
indicators may not properly utilize the indicator until the device is
rebooted at least once after first install, if the garbage collector
wins the race and finalizes the necessary PrivacyConfig callback.

Test: Manual: Boot and unlock a device and wait about a minute for it
to settle. Run `adb shell "dumpsys activity service \
com.android.systemui | grep locationAvailable"`. It will return two
results with matching values. Then, run `adb shell cmd device_config \
put privacy location_indicators_enabled false` (or `true`; whichever
does not match the value seen earlier) to change the values. Finally,
run the first adb command again to verify that both of the values for
locationAvailable match and reflect the newly-specified value.

Issue: calyxos#1648
Change-Id: I4ee1d5054a8bb294cea267034169c6615490a735
Signed-off-by: Mohammad Hasan Keramat J <[email protected]>

Devices with OLED display suffer from
status-bar's notification items and nagivation bar's software keys
causing permanent burn-ins when used long-term.

Moving all items in the area
both horizontally and vertically workarounds this problem.

This new feature can be enabled by setting
config_statusBarBurnInProtection to true.

The shifting interval can be configured with config_shift_interval.
The default shifting interval is 60 seconds.

Forward-ported to oreo-mr1.

Change-Id: I8df1ebc8bc0f359fe5a6a1fe11aa6201237a7359

SystemUI: rework statusbar burn-in protection controller

* Turns out that this controller was instantiated twice resulting in two timers running simultaneously which resulted in views to shift abruptly.
  Since the shift amount was too low it was not noticeable at all. So now we instantiate it once with all final dependencies and inject PhoneStatusBarView in fragment transaction.
* Finalized many instance variables and a reference to the main handler is kept instead of creating new ones in each cycle
* simplified / generalised the shift algorithm a bit so that it's easily configurable
* added a callback to reload shift vars on screen density changes
* additional changes:
* use the same controller for navigation handle, saves some cpu time

Signed-off-by: jhonboy121 <[email protected]>

SystemUI: inject BurnInProtectionController

Signed-off-by: jhonboy121 <[email protected]>

[jhonboy121]: use the scoped SysUISingleton annotation

SystemUI: BurnInProtectionController: rewrite in kotlin and improvements
* ditched TimerTask in favor of coroutines

Signed-off-by: jhonboy121 <[email protected]>

[jhonboy121]:
* adapted to A13
* use BurnInHelper util functions for calculating offset

[ghostrider-reborn]:
* use NavigationBarView directly instead of CentralSurfaces
* rework timer and offset calculation logic

SystemUI: Enable statusbar burn-in protection by default

 * AOSP already provides a config for burn-in protection
   so enable statusbar burn-in protection based on that

 * To forcefully disable it, set
   config_statusBarBurnInProtection to false

Change-Id: I1a0b5c06ed6092153a35cb1cdc12b3b5e865ce8f

SystemUI: BurnInProtectionController: offset less aggressively

Change-Id: Ib37b0fde6edfc34cad8876d2e01ba4f37f323036
Signed-off-by: jhonboy121 <[email protected]>

SystemUI: Make setNavigationBarView and setPhoneStatusBarView nullable

 * this fixes a potential npe on devices without navbar or statusbar

Change-Id: Ia8e0ff844e24f67685ba20ac61a88d3256c9c648

Co-authored-by: jhonboy121 <[email protected]>
Co-authored-by: Adithya R <[email protected]>
Co-authored-by: Fabian Leutenegger <[email protected]>
Change-Id: I067022d43d20f43760a192b43569c31316a5337a
Signed-off-by: Adithya R <[email protected]>

Animations slow down the phone. Gotta go fast especially while
wake-and-unlocking with capacitive fingerprint scanners.
Like @ jesec said in LineageOS/android_frameworks_base@32244a3,
OEMs have been doing this for years.

Based on:

Author: Rishawn <[email protected]>
Date:   Mon Jan 10 09:47:15 2022 +0530

    SystemUI: Allow disabling ripple effect on unlock [1/2]

    neobuddy89:
    * Reverse logic. Enabled animation by default.

Author: Nauval Rizky <[email protected]>
Date:   Wed Jan 19 08:31:56 2022 +0700

    SystemUI: Fix method for disabling unlock ripple animation

    NotificationShadeWindowController's are not gracefully closed, which
    leads to top parts of the screen is being obscured by invisible shade window.
    And also, "ripple" is actually still exists due to lightRevealScrim are
    being started by onKeyguardFadingAwayChanged, which is not what user expect
    when they want to disable the effect.

    So in order to handle those cases, lets intercept it from the
    AuthRippleController instead.

    [palaych] With system settings we need to pass UserHandle.USER_CURRENT to make sure we are getting proper value.

    Change-Id: I85ab96368c8b0099700f3de18ba95ce63eaac443

Co-authored-by: Rishawn <[email protected]>
Co-authored-by: Nauval Rizky <[email protected]>
Change-Id: I12f152e2c62b22ec75bcf86591721de01ab39c70

On some devices, transition from AOD_PAUSED state (when display is
turned off when the proximity sensor is covered) back into AOD state
(when it is no longer covered), is broken and results in screen staying
black until it is turned on using the power button. This can be worked
around by switching the display into the ON state briefly (1 sec)
before coming back into the DOZE_AOD state.
Note that this does not enter the fully on state (lockscreen), the only
visible change is in brightness.

To enable this workaround, enable this in the device's SystemUI overlay:
config_displayTurnsOnWhenResumingAod

Change-Id: I05ebd5402c0789dd095ea5b0e1af6204d84c5a65

Squashed:
SystemUI: Hide notification scrim background when entering split shade

Change-Id: I191b9e17d85931f029657abecf9ed648d11e19ae
[neobuddy89: Adapted for A14 QPR1]
Signed-off-by: Pranav Vashi <[email protected]>

…or brightness curve"

This reverts commit ed7e7e4.

Change-Id: Idf19a5c6ba20257ee48557975f5536d0501e6ab6

…s slider

Backlight values are already gamma corrected.

Change-Id: I83b38a1334b8df156e4e53b06243c48d565be5d5
Co-authored-by: minaripenguin <[email protected]>
Co-authored-by: Cosmin Tanislav <[email protected]>

Bumps [word-wrap](https://github.com/jonschlinkert/word-wrap) from 1.2.3 to 1.2.5.
- [Release notes](https://github.com/jonschlinkert/word-wrap/releases)
- [Commits](jonschlinkert/word-wrap@1.2.3...1.2.5)

---
updated-dependencies:
- dependency-name: word-wrap
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>